Category: Geeks r Us
Okay, so my counselor finally got me the new Window-Eyes upgrade that I'd been lusting after so that I could do homework on Blackboard in the comfort of my own freaking dorm room, instead of being constricted to only working in the disabilities services office during the day. While reserching this upgrade, I must have missed something crucial, because I had no freaking clue that Window-Eyes 7.5.3 wasn't compatible with Vista. But wouldn't one think that while checking for eligibility of an upgrade, the site might not only tell me that my screenreader was out-of-date, but that I also was not eligible for an upgrade because my system was obscilete? I am just fucking saying. My brain having been so fried because of school, I didn't think to reiterate what kind of system I had to my counselor and her assistant, who were purchasing the software, becaus it should also be in my case notes since they've purchased technology for me before. I'm wondering what to do about this. Could they have perhaps assumed that I was using Windows 7 and coded the software to be geared toward that? Are there subversions of the new upgrade that would be compatible with Vista Home Premium, 32-bit? I am quite frazzled, as you can see, or can't, or whatever, and am not usually this technologically challenged, but I think the times are catching up with me. HELP!!
Hi. This comes straight from the GW Micro upgrade page...
all
32-bit and 64-bit versions of Windows Vista, Windows Server 2008, and Windows 7 are
supported with this upgrade. Any version of Windows prior to Windows XP is not supported. So, you might want to give GW Micro a call and see what they can do for you. My guess is that whoever paid for the upgrade may have chosen the wrong kind of copy-protection, because window-eyes has a few different kinds depending on your situation. If you call them and let them see any error messages you have, I bet you they can help you fix it. They're good folks, much better than some companies inSt. Petersburg florida that I could name, but will not. grin
That would mean they'd have to re-code a CD and send it to me again, wouldn't it? And yeah, after thinking about it more indepth, I kind of drew the same conclusion. I had forgotten that, once during my freshman year, I tried to install the driver thing on a school computer so I could use a pocket version on my thumb-drive, and since it was Vista 64, it wouldn't work. Kind of annoying. But yeah, I'm pretty sure you're right and that's what happened. Going to wait to hear from my counselor to see if they need to be involved in the troubleshooting process or not. Thanks!
Let me know what happens, i'm curious to know. i hope they can help you!
Never had a problem with FS, Chris.
If it works on a fresh install I'd simply remove it complete from the computer and start over. You'll need to remove it with remove programs, and also in the program files, but this will require sighted help.
Calling them sounds like a good fix. They'll probably have you remove the file that has the code and then reinstall. That way you'll have speech while you work.
Okay, update: So the problem I tought might have been gong on actually is a non-issue now. With previous versions of Window-Eyes, the incompatibility with system types was possible, but now, I guess, Window-Eyes is more versatile and workds across all systems without needg variations. So, the guy on the phone, when I finally got tired of using NVDA lol, just had me route to the Setup file in a different way and it eventually worked. Yay! So guys, if ths ever happens to you, instead of telling it to open Setup.exe in the autoplay dialog, go to "Open Folder to View Files," click the "Wineyes" folder, and press S until you hit Setup.exe, then proceed that way.